Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Sample response file template

The sample response file template shows the sample response file, oesetup.ini, from which you can define your unique response file. This file was recorded using the -r option, during an installation of all OpenEdge products. Default values were used where possible.

Response file template

Progress Software Company recommends that you use the response file template from which to create a unique response file. The following sample file, install.ini, shows the response file template. It presents the structure and entries you need to create a response file.

Note: The number of OpenEdge products, components, and subcomponents you identify for installation might vary from those shown in the sample file , but all other sections that appear must be retained.

install.ini

[Configuration Count] NumberofConfigurations=n [Product Configuration 1] name=Company_name serial=serial_number version=version_number control=control_number_1 control_number_2 control_number_3 prodname=Product_name . . . [Product Configuration n] name=Company_name serial=serial_number version=version_number control=control_number_1 control_number_2 control_number_3 prodname=Product_name [Type and Destination] ; Type is COMPLETE or CUSTOM type=CUSTOM path=directory-pathname/dlcsilent workpath=directory-pathname/wrk [Server Engine] ; ; Required for database products ; 4GL ; SQL ; BOTH type=SQL [SonicEsbAdapter] esbcontainername=xxxxxxxxxxxxxxx esbdomain=Domain1 esburl=tcp://<localhost>:<port-number> esbusername=Administration esbpassword=Administration esbpath=<path to Sonic ESB installation or blank> [[WebServer] ; Type NSAPI ; Type CGI (If the type is CGI then the CgiScriptPath MUST exist) WebServerType=CGI CgiScriptPath=directory-pathname/silentCgiScriptDir CopyHtmlFiles=yes DocumentRootPath=directory-pathname/silentDocRootDir

[Language Default] _szDefaultLanguage=English - American [Language Choice] ;complete list of supported languages listed in "Packaging" section of Appendix D "OpenEdge National Language Support." ;lang=Arabic ;lang=Chinese (Simple) ;lang=Chinese (Traditional) . . . ;lang=Swedish ;lang=Thai ;lang=Turkish lang1=Czech lang2=Dutch land3=English - America [International Settings] ; See intlsets.txt on your CD or DVD for acceptable values cpinternal=ISO8859-1 cpcollation=Basic cpcase=Basic dateformat=mdy numsep=46 numdec=44 ;See table xxx for an explanation of the numsep and numdec values. [WSA] ; 0 to enable authentication ; 1 to disable authentication disableWsaAuthentication=1 webServicesUrl=http://<hostname>:<port-number>/wsa/wsa1 [Java] ; ; Required for platforms where the user must install Java. For Lava details ;specified by platform, see "Java requirements" section. ; jdkHomePath=/<jdk-path>

[WSA] ; 0 to enable authentication ; 1 to disable authentication disableWsaAuthentication=1 webServicesUrl=http://<hostname>:<port-number>/wsa/wsa1 [Installed Products] ; Details about the total number of products, each installed product’s name ; and installed components and subcomponents Product Count=nn Product Name _Components _Subcomponents . . . Product Name _Components _Subcomponents

If you receive a warning message at the beginning of your installation stating that the detected JVM version does not match the version supported by OpenEdge, you can add an entry in the .ini file to allow batch installs to override this warning. Add the following entry to the [java] section of the .ini file if you want the installation to continue after detecting a mismatched JVM version:

jvmAllowUnSupported=yes